Crew Chief continuously logs all kinds of infomation in its "Console window" and when Crew Chief exits it saves it all in a file in the folder <Documents>\CrewChiefV4\debugLogs (for example c:\users\Documents\<your name>\CrewChiefV4\debugLogs).  Each one has a timestamp in the name which is the date and time when it was saved (for example c:\users\Documents\<your name>\CrewChiefV4\debugLogs\console_2022_03_23-20-12-26.txt, year_month_day-hour-minute-second). It keeps the latest 25 files, deleting older ones.

You can also save a file at any time by right clicking on the Console window.

A "running total" of the more serious errors are written to debugLogs\ErrorLog.txt as well as the console log.

If Crew Chief runs but isn't working for you then the most important thing is to upload the log file that was saved after you saw a problem to either the forum, Discord or to the confidential email address


If that doesn't help then collecting a "repro trace" of all the things Crew Chief does will give more information. To do this:

Open the Run prompt (Win+R) then type:

"%ProgramFiles(x86)%\Britton IT Ltd\CrewChiefV4\CrewChiefV4" -DEBUG


or open a Command Prompt (by typing cmd in start menu) then type:

cd /d "%ProgramFiles(x86)%\Britton IT Ltd\CrewChiefV4"
CrewChiefV4 -DEBUG


Either way Crew Chief should now be running in debug mode:



If Crew Chief crashes you can help by collecting a "boot trace".

Open the Run prompt (Win+R) then type:

"%ProgramFiles(x86)%\Britton IT Ltd\CrewChiefV4\CrewChiefV4" -DEBUG
> c:\temp\output.txt 2>&1

or open a Command Prompt (by typing cmd in start menu) then type:

cd /d "%ProgramFiles(x86)%\Britton IT Ltd\CrewChiefV4"
CrewChiefV4 -DEBUG
> c:\temp\output.txt 2>&1

Then c:\temp\output.txt contains the messages which can be used by the dev team.  The console log file won't be saved but a previous one may help.



Crew Chief Forum

Discord channel